How to turn off bluetooth dial

You might want to take a few minutes to read the user guide from your headset. Many headsets will allow for using with the phone, and have a number of settings for each button. The phone is dialing because the headset is sending it the command to dial. Many headsets work in this manner. I have a Blue Ant and when I double tap the button it activates the phone dialer. I believe you just might be misunderstanding the function of your headset.

I have the same issue - Beoplay H7 headphones. I've ended up accidentally calling the last number a few times. Seems like such a weird unintuitive 'feature'. No options in the Beoplay app to control this behaviour.

Such awful, unhelpful responses. Blame the headset? RTFM, ChrisJ4203? Blame the user's "attitude"? Really, KiltedTim? Apple is perfect and the device is the problem? Seriously?

The long-push-redial function is very common on Bluetooth headsets, not just one special instance.

The answer is no, it's not possible. Apple has chosen not to give you control over whether Siri or connected devices can initiate phone calls.

You need to dial a dummy phone number after each call you make if you wish to be sure you don't accidentally redial a real number.

To stop Siri dialling a number when it mishears you, you need to delete all your contacts or completely disable Siri.

Thanks, Apple!

Why am I replying to a two year old thread? It's the top result on Google for "how to disable bluetooth dialling iphone". And all it has is smarmy nonsense responses.

To Apple:

Please fix this.

Allow users to disable Siri dialling so it doesn't mishear names and start dialling them.

Allow users to disable Bluetooth redialling.

Or at least allow a confirmation prompt before dialling like the OP requested.

I know you don't like cluttering your UI with settings, but really, redialling without confirmation if you press a button in the wrong way is awful UX. Apple, you're able to fix it, please do it already.

That's a function of the headset, most likely. The behavior of most of the jawbone headsets can be changed by plugging it into your computer and updating it via their web site.

LOL, if I had a dime for everything that Apple ever left broken by intention I'd be a literal billionaire. (Dictionary definition of literal. Not hyperbolistic definition. I would *actually*... be... a billionaire.) -- Intentionally breaking something doesn't make it fixed. It makes it broken exactly as intended. This principle in car manufacturing is called Built In Obsolescence. It represents a scheduled inadequacy that propels consumption rather than appeasement of human needs. (Apple does this with OS compatibilities biannually.) And when your *intentional* design, has a flaw... it is what's known in engineering throughout the world as: A Design Flaw. -- If the only factor we used to define a fault were 'intention'... Hitler would have been "functioning exactly as intended" and therefore flawless. Which is frankly ridiculous. I doubt it will happen, but let's all hope this little lesson in design vernacular is over.

All that's needed is a 'enable/disable bluetooth dial last number' option in iPhone settings somewhere. This is an improvement rather than a fix per se.

Just because somebody designed this feature and made it part of a protocol doesn't mean its useful or good. In fact, in my case its completely useless and has only resulted in accidental calls.

Congratulations on reviving a thread that's been dead for 2 years with your own nonsense.

You're not talking to Apple, by the way.

If it hurts when you hit your foot with a hammer, then don't do that! Try paying attention to what you're doing and you won't have problems.

You know what... figure it out yourself. Copping an attitude will not get you very far around here.

And yet again... This thread is 3 years old. Your experience has NOTHING to do with this thread.

Just leaving an annoying reply because you are being an *******.

Much like Crissa's headset, KT is also very old and does not have specific drivers any filters. Just guessing.

I appreciate your response, regardless how far after the fact. - It's 2017. Still not fixed.

It's not fixed because it's not broken. It's operating as it was intended.